home *** CD-ROM | disk | FTP | other *** search
- Hi Rich -
-
- The choice between IMAP and POP basically boils down to what you want to
- do. If you want an environment where:
- 1) the server is merely a mail drop, the client will pick up and delete
- messages from the server.
- 2) long-term storage of mail is on the client.
- 3) the user only uses a single client (since the mail is stored there).
- then POP is probably alright for your needs.
-
- IMAP gives you much more flexibility. It can be used in the POP model,
- but it can also be used in a model in which all mail is stored remotely and
- the client manipulates mail on the server. This makes it possible to use
- mailboxes that are far larger than the available resources on the client, and
- also makes it possible to use multiple clients. Or, using c-client software
- you can have a hybrid model, with some mail on the server and some on the
- client. Also, IMAP provides a search and RFC-822 parsing engine on the
- server, so the client does not have to do these if it doesn't want to.
-
- I routinely monitor multiple mailboxes from my workstation at home and
- the office, with complete transparency (I have more personal mail going to my
- machine at home). I also use MailManager (NeXT), Pine, MS, and Mailstrom
- fairly regularly, depending upon which machine I am sitting in front at the
- time. None of these programs in any way affects the usability of mail with
- any other.
-
- The bottom line: the choice is between (extreme) simplicity and
- flexibility. IMAP can do what POP does, at the cost of somewhat more complex
- software that implements all the stuff you don't use. If you do decide to go
- the POP route, the IMAP toolkit includes a POP server that some people
- consider a lot easier to work with than the standard POP servers floating
- around the net.
-
- I would recommend against cc:Mail under any circumstances. Read the
- USENET messages on comp.mail.misc about problems with cc:Mail.
-
- -- Mark --
-
-
-
-